CassandraSinkCluster fix lost messages #1845
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rukai
force-pushed
the
cassandra_sink_cluster_fix_lost_messages
branch
from
1d2b9b1 to
799789b
Compare
rukai
force-pushed
the
cassandra_sink_cluster_fix_lost_messages
branch
from
799789b to
38817c5
Compare
CodSpeed Performance ReportMerging #1845 will not alter performanceComparing Summary
|
rukai
force-pushed
the
cassandra_sink_cluster_fix_lost_messages
branch
from
0e3c6ac to
a3eedcb
Compare
justinweng-instaclustr
approved these changes
Nov 26, 2024
ronycsdu
approved these changes
Nov 26, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
closes #1843
On my local machine:
I dont think this issue is common enough to rush out a release for, but this intermittent failure did turn out to be a real issue.